boot me

Bien que n'étant pas un spécialiste Wii, j'ai rencontré ce problème.

J'ai simplement réinstallé l'Homebrew Channel en lançant Hackmii installer et tout est redevenu normal
1- Télécharger Hackmii installer
2- Décompresser hackmii_installer_v1.2.zip
3- Aller dans le dossier hackmii_installer_v1.2
4- Copier le fichier boot.elf
5- Insérer votre carte SD dans le PC
6- Aller dans le dossier apps de la carte SD
7- Créer un dossier HackMii et coller le fichier boot.elf dedans
8- Insérer la carte SD dans la Wii
9- Lancer l’homebrew channel
10- Lancer HackMii

Pour la suite, il suffit de suivre ce tutoriel à partir de la phrase "Patientez un petit moment puis appuyez sur le bouton 1 :"

Problème résolu ! J'ai fini par formater !
Apparement, c'est un problème des Asus portables, pour booter en uefi il faut que le fichier .efi en 64bits, soit de chemin suivant :

EFI/Microsoft/boot/bootmfr64.efi

Un retour avec des éléments complémentaires de Saurik alias Jay Freeman, développeur renommé de Cydia
Il a enlevé le paquet "Pangu 7.1-7.1.x Untether" (version 0.3) de Cydia après l'obtention d'une demande de l'équipe Pangu, car ils estiment qu'il pourrait y avoir un problème qui affecte certains utilisateurs qui passent par des versions précédentes. Il a fourni les informations suivantes sur reddit:

[+] CLIQUER POUR AFFICHER

I spent a bunch of time talking to someone from Pangu before releasing this (including asking them to reimplement the installation scripts of the package, which I felt had issues). One thing in particular I wanted to verify with them was that this version of the untether did not have any known regressions from previous versions, as I did not want to release something with any regressions as an upgrade.

This is actually an interesting corner case when dealing with upgrades, and is the reason sometimes why a jailbreak might come with a newer version of Cydia, or a newer untether, than you see an upgrade pushed for: if the stuff installed by a jailbreak doesn’t work immediately after it is installed, that’s a different and more reasonable scenario than if you had a setup that was working that suddenly is broken.

Even if only one in a thousand users, or one in tens of thousands of users, are affected by a bug, pushing it out as an upgrade causes a large number of immediate failures, often which are more serious than failures during an installation process (where it is more expected something will go wrong, the user doesn’t have as much data, likely just restored their device, was told to have a backup handy, etc.).

In fact, this is why (apparently) there was no 0.2 release as a package: while there was an interesting fix (the light sensor issue), the new untether covered fewer devices than the previous 0.1 release with the same stability. With the 0.3 release, however, it was thought by Pangu that they had fixed all of these issues, and that the only remaining bugs were ones that had affected all previous releases.

However, Pangu currently believes there might be an issue that is affecting some users upgrading from previous versions, and has asked me to pull their package. It is not entirely clear whether these are real new issues or whether these are simply cases where the user hasn’t rebooted in a long time. (It also needs to be determined whether these are just broken extensions, and are fixable with Volume Up.)

(That’s actually a really common confounder: it could very well be that rebooting is going to cause the user’s device to not boot, because they deleted or corrupted some critical file. People don’t reboot that often, though, so packages that ask users to reboot get tons of actually-unrelated “this made my device no longer boot” issues that were truly caused days or weeks earlier by something entirely different.)

(My current guess, FWIW, is that there is some new issue in the 0.2 and 0.3 releases that was not present in the 0.1 release, and that the people who are having issues are having issues are some subset of the 0.1 people who are now upgrading to 0.3. 0.2 and 0.3 use a different exploit than 0.1 that seems a little more finicky, causing the occasional green screens while booting where it has to retry.)

Ah oui en effet c'est devenu payant Ce n’était pas le cas avant. D’ailleurs je me demande de quel droit ils vendent Linux...

Y'a le LiveCD Linux Parted Magic qui est super pour (essayer de) réparer les partitions, récupérer les données et autres problèmes de disques :p A mettre sur clé USB avec UNetbootin.

Sinon pour éviter ce genre de désagrément lié au multi-boot, je met Windows et Linux sur des disques durs différents et je me sert du menu Boot du BIOS pour choisir sur quel disque je boot

Je crois même que ça a flingé la partition Windows ....
Bon, plus qu'a tout réinstaller et tout perdre ...

Bon, j'ai suivile tuto à la lettre, le pc detecte même plus windows ...